Repository navigation
docs(upstream): record v0.42.5 through v0.42.8 - #198
Merged
Merged
Conversation
The two triaged issues the 1.5.0 round left open have shipped: #1495 Kotlin callable signatures in v0.42.6, and #1482 / #1482b TS export-alias plus .js-specifier resolution in v0.42.8. The ledger still listed both as open work, so a future sync would either redo them or spend time discovering they were done. Tracked parity stays 1.5.0. None of these four releases is an upstream-range port: #1495 is a documented divergence FROM upstream, whose own hook returns undefined because it looks the parameter list up through a grammar field that does not exist; #1482 and #1482b close upstream-triaged issues rather than upstream commits; and the other two are project-local -- an invention of ours reverted, and a P1 from the Godot-team liaison doc. Also records what the liaison-doc fix deliberately did NOT do, since the suggestion looked reasonable and will occur to someone again: rolling the newest building state slot back to the previous current would present a database that no longer exists as authoritative. The slots carry state, not data.
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #198 +/- ##
==========================================
+ Coverage 95.13% 95.15% +0.01%
==========================================
Files 136 136
Lines 71817 72219 +402
==========================================
+ Hits 68326 68722 +396
- Misses 3491 3497 +6 see 3 files with indirect coverage changes 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Ledger-only. Four releases landed since the ledger was last touched, and it still
described two of them as open work.
v0.42.55aff695(#190).codegraph-v2to.codegraphv0.42.681628f2(#192)v0.42.720e3f9d(#194)v0.42.84a17919(#196).js→.tsresolutionAll four published with
isDraft=falseand 7 assets. Workspace count afterv0.42.8: 127 suites / 3134 passed / 0 failed.Tracked parity stays
1.5.0Stated explicitly, because four releases in a row could easily be misread as parity
movement. None of them is an upstream-range port:
kotlin.tslooks theparameter list up through a grammar field the Kotlin grammar does not expose, so
its hook always returns
undefined. We had mirrored that. The fix reuses theby-KIND traversal already sitting ten lines away in the same file.
upstream's
.codegraph, and the single P1 from the Godot-team liaison doc.The 26 DEFER items and
0682137remain exactly as they were.Two findings recorded so a future sync does not re-derive them
Python has no export semantics —
find_exported_symbolrequiresis_exportedand the Python spec never sets it, upstream included. This isload-bearing for #1482's scoping.
The double-buffered state slots carry STATE, not DATA. This is why the liaison
doc's suggestion — roll the newest
buildingslot back to the previouscurrent—was refused. The rebuild publishes
buildingdurably before deleting the database,so that older slot describes a database that no longer exists; measured aftermath
was 4096 bytes and
nodes=0against 1098/1221 intact. Presenting it asCurrentwould turn every query into a silent empty answer. The suggestion looked reasonable
and will occur to someone again, so the reasoning is now written down.
Verification
make fmtidempotent; onlydocs/upstream-sync/UPSTREAM.mdchanged.git logandgh release view.Cargo.tomlversion, DEFER dispositions, and the earlier entriesuntouched.